Crowdsourced remote start for vehicle

ABSTRACT

A server includes a processor, programmed to receive a vehicle location from a vehicle, receive a weather condition of the vehicle location from a cloud server, responsive to receiving a calendar of a user including an event, calculate a departure time based on the vehicle location and a location of the event, responsive to receiving a desired cabin temperature of the user from a mobile device, calculate a minimum time for the vehicle to reach the desired cabin temperature based on the weather condition, calculate a vehicle start time using the departure time and the minimum time, and send an instruction to the vehicle to start at the vehicle start time.

TECHNICAL FIELD

The present disclosure generally relates to a vehicle remote startsystem. More specifically, the present disclosure relates to a systemcontroller vehicle remote start based on temperature.

BACKGROUND

Many vehicles are provided with remote start features to allow a user tostart vehicle engine remotely before starting to use the vehicle. Thisfeature may be particularly useful when the user desired temperature inthe vehicle cabin is significantly different from the ambienttemperature (e.g. in a cold winter or hot summer day). The user may usea remote control to transmit a radio-frequency (RF) signal to thevehicle to command the vehicle to start while within a short range fromthe vehicle. Additionally or alternatively, a remote control command maybe transmitted to the vehicle via a wireless network (e.g. cellularnetwork) from a mobile device operated by the user.

SUMMARY

In one or more illustrative embodiments of the present disclosure, aserver includes a processor, programmed to receive a vehicle locationfrom a vehicle, receive a weather condition of the vehicle location froma cloud server, responsive to receiving a calendar of a user includingan event, calculate a departure time based on the vehicle location and alocation of the event, responsive to receiving a desired cabintemperature of the user from a mobile device, calculate a minimum timefor the vehicle to reach the desired cabin temperature based on theweather condition, calculate a vehicle start time using the departuretime and the minimum time, and send an instruction to the vehicle tostart at the vehicle start time.

In one or more illustrative embodiments of the present disclosure, amethod for a server includes receiving a user profile from a mobiledevice associated with a user identifying a vehicle for a ride and adesired cabin temperature; receiving a vehicle location, a vehicleperceived condition, a vehicle configuration, and a vehicle historictemperature from the vehicle as identified; obtaining a calendarassociated with the user including an event having an event location;calculating a departure time based on the vehicle location and the eventlocation; receiving a weather condition of the vehicle location from acloud server; calculating a minimum time for the vehicle to reach thedesired cabin temperature based on the weather condition, the vehicleperceived condition, the vehicle configuration, and the vehicle historictemperature; calculating a vehicle start time using the departure timeand the minimum time; and sending an instruction to the vehicle to startat the vehicle start time.

In one or more illustrative embodiments of the present disclosure, anon-transitory computer-readable medium includes instructions that, whenexecuted by a processor of a computer, cause the computer to receive auser profile from a mobile device associated with a user identifying avehicle for a ride and a desired cabin temperature; receive a vehiclelocation, a vehicle perceived condition, a vehicle configuration, and avehicle historic, temperature from the vehicle as identified; obtain acalendar associated with the user including an event having an eventlocation; calculate a departure time based on the vehicle location andthe event location; receive a weather condition of the vehicle locationfrom a cloud; calculate a geofence enclosing the vehicle location;responsive to identifying a plurality of fleet vehicles within thegeofence, receive a fleet vehicle perceived condition, a fleet vehicleconfiguration, and a fleet vehicle historic temperature from the fleetvehicles; calculate a minimum time for the vehicle to reach the desiredcabin temperature based on the weather condition, the vehicle perceivedcondition, the vehicle configuration, the vehicle historic temperatureas received from the vehicle, the fleet vehicle perceived temperature,the fleet vehicle configuration, and the fleet vehicle historictemperature as received from the fleet vehicles; calculate a vehiclestart time using the departure time and the minimum time; and send aninstruction to the vehicle to start at the vehicle start time.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the invention and to show how it may beperformed, embodiments thereof will now be described, by way ofnon-limiting example only, with reference to the accompanying drawings,in which:

FIG. 1 illustrates an example block topology of a vehicle system of oneembodiment of the present disclosure;

FIG. 2 illustrates an example schematic diagram of a vehicle system ofone embodiment of the present disclosure; and

FIG. 3 illustrates an example flow diagram of the vehicle system of oneembodiment of the present disclosure.

DETAILED DESCRIPTION

As required, detailed embodiments of the present invention are disclosedherein; however, it is to be understood that the disclosed embodimentsare merely exemplary of the invention that may be embodied in variousand alternative forms. The figures are not necessarily to scale; somefeatures may be exaggerated or minimized to show details of particularcomponents. Therefore, specific structural and functional detailsdisclosed herein are not to be interpreted as limiting, but merely as arepresentative basis for teaching one skilled in the art to variouslyemploy the present invention.

The present disclosure generally provides for a plurality of circuits orother electrical devices. All references to the circuits and otherelectrical devices, and the functionality provided by each, are notintended to be limited to encompassing only what is illustrated anddescribed herein. While particular labels may be assigned to the variouscircuits or other electrical devices, such circuits and other electricaldevices may be combined with each other and/or separated in any mannerbased on the particular type of electrical implementation that isdesired. It is recognized that any circuit or other electrical devicedisclosed herein may include any number of microprocessors, integratedcircuits, memory devices (e.g., FLASH, random access memory (RAM), readonly memory (ROM), electrically programmable read only memory (EPROM),electrically erasable programmable read only memory (EEPROM), or othersuitable variants thereof) and software which co-act with one another toperform operation(s) disclosed herein. In addition, any one or more ofthe electric devices may be configured to execute a computer-programthat is embodied in a non-transitory computer readable medium that isprogramed to perform any number of the functions as disclosed.

The present disclosure, among other things, proposes a vehicle remotestart system configured to start the vehicle at a correct timecalculated that the vehicle reaches a desired cabin temperature when theuser starts to use the vehicle while minimizing idling and fuelconsumption.

Conventionally, a vehicle user may manually control the remote startfeature of a vehicle. For instance, the user may manually activate thevehicle remote start at an arbitrary time (e.g. 10 minutes) before ascheduled ride estimated that the vehicle will reach a desired cabintemperature via HVAC when the user starts the ride. However, this userestimated time may be inaccurate. If the vehicle starts too early, fuelmay be wasted and vehicle component life may be reduced as some enginesare not made to idle for long periods and HVAC component lifespan may bereduced. On the contrary, if the vehicle starts too late, it may not yetreached the desired cabin temperature when the user starts the ride,causing inconvenience and bad user experience. Additionally, due tofactors such as weather condition, vehicle model, it may be difficultfor the user to accurately estimate the correct time to start thevehicle.

The present disclosure proposes a system to more accurately calculate atime to start to vehicle. With various information including weathercondition, vehicle model/configuration, vehicle year, fuel level or thelike, the system may estimate the amount of time it will take for avehicle to achieve a user-specified cabin temperature. The vehicle usermay input into a mobile application his/her scheduled departure time.The scheduled departure time may be used only once, or alternatively setas a recurring event on certain days of the week. The mobile applicationmay be configured to be associated with a calendar of the user toautomatically obtain a scheduled departure time of a ride. With theestimated amount of idling time and the departure time, the system maydetermine the correct time to start the vehicle to achieve the desiredtemperature while minimizing fuel consumption.

Furthermore, to increase the accuracy of time calculation, the systemmay further utilize crowdsourced information from connection fleetvehicles and histories of cabin temperature for idling vehicles. Forinstance, a machine learning model may be created for all fleet vehicleswithin a geofence (e.g. a zip code). The model may take into accountvarious information such as current outside weather condition (e.g.temperature, wind chill), vehicle perceived weather information (e.g.sun, shade, level, vehicle heading), and/or vehicle characteristics(e.g. model, configurations of HVAC components, engine characteristics).Additionally, the system may be configured to override commands if thevehicle is currently in an enclosed space such as a garage detectedusing vehicle sensors.

Referring to FIG. 1, an example block topology of a vehicle system 100of one embodiment of the present disclosure is illustrated. A vehicle102 may include various types of automobile, crossover utility vehicle(CUV), sport utility vehicle (SUV), truck, recreational vehicle (RV),boat, plane, or other mobile machine for transporting people or goods.In many cases, the vehicle 102 may be powered by an internal combustionengine. As another possibility, the vehicle 102 may be a batteryelectric vehicle (BEV), a hybrid electric vehicle (HEV) powered by bothan internal combustion engine and one or move electric motors, such as aseries hybrid electric vehicle (SHEV), a plug-in hybrid electric vehicle(PHEV), or a parallel/series hybrid vehicle (PSHEV), boat, a plane orother mobile machine for transporting people or goods. As an example,the system 100 may include the SYNC system manufactured by The FordMotor Company of Dearborn, Mich. It should be noted that the illustratedsystem 100 is merely an example, and more, fewer, and/or differentlylocated elements may be used.

As illustrated in FIG. 1, a computing platform 104 may include one ormore processors 106 configured to perform instructions, commands, andother routines in support of the processes described herein. Forinstance, the computing platform 104 may be configured to executeinstructions of vehicle applications 108 to provide features such asnavigation, remote controls, and wireless communications. Suchinstructions and other data may be maintained in a non-volatile mannerusing a variety of types of computer-readable storage medium 110. Thecomputer-readable medium 110 (also referred to as a processor-readablemedium or storage) includes any non, transitory medium (e.g., tangiblemedium) that participates in providing instructions or other data thatmay be read by the processor 106 of the computing platform 104.Computer-executable instructions may be compiled or interpreted fromcomputer programs created using a variety of programming languagesand/or technologies, including, without limitation, and either alone orin combination, Java, C, C++, C#, Objective C, Fortran, Pascal, JavaScript, Python, Perl, and PL/SQL.

The computing platform 104 may be provided with various featuresallowing the vehicle occupants/users to interface with the computingplatform 104. For example, the computing platform 104 may receive inputfrom human-machine interface (HMI) controls 112 configured to providefor occupant interaction with the vehicle 102. As an example, thecomputing platform 104 may interface with one or more buttons (notshown) or other HMI controls configured to invoke functions on thecomputing platform 104 (e.g., steering wheel audio buttons, apush-to-talk button, instrument panel controls, etc.).

The computing platform 104 may also drive or otherwise communicate withone or more displays 114 configured to provide visual output to vehicleoccupants by way of a video controller 116. In some cases, the display114 may be a touch screen further configured to receive user touch inputvia the video controller 116, while in other cases the display 114 maybe a display only, without touch input capabilities. The computingplatform 104 may also drive or otherwise communicate with one or morespeakers 118 configured to provide audio output and input to vehicleoccupants by way of an audio controller 120.

The computing platform 104 may also be provided with navigation androute planning features through a navigation controller 122 configuredto calculate navigation routes responsive to user input via e.g., theHMI controls 112, and output planned routes and instructions via thespeaker 118 and the display 114. Location data that is needed fornavigation may be collected from a global navigation satellite system(GNSS) controller 124 configured to communicate with multiple satellitesand calculate the location of the vehicle 102. The GNSS controller 124may be configured to support various current and/or future global orregional location systems such as global positioning system (GPS),Galileo, Beidou, Global Navigation Satellite System (GLONASS) and thelike. Map data used for route planning may be stored in the storage 110as a part of the vehicle data 126. Navigation software may be stored inthe storage 110 as one the vehicle applications 108.

The computing platform 104 may be configured to wirelessly communicatewith a mobile device 128 of the vehicle users/occupants via a wirelessconnection 130. The mobile device 128 may be any of various types ofportable computing devices, such as cellular phones, tablet computers,wearable devices, smart watches, smartfobs, laptop computers, portablemusic players, or other device capable of communication with thecomputing platform 104. A wireless transceiver 132 may be incommunication with a Wi-Fi controller 134, a Bluetooth controller 136, aradio-frequency identification (RFID) controller 138, a near-fieldcommunication (NFC) controller 140, and other controllers such as aZigbee transceiver, an IrDA transceiver, a ultra-wide band (UWB)controller (not shown), and configured to communicate with a compatiblewireless transceiver 142 of the mobile device 128.

The mobile device 128 may be provided with a processor 144 configured toperform instructions, commands, and other routines in support of theprocesses such as navigation, telephone, wireless communication, andmulti-media processing. For instance, the mobile device 128 may beprovided with location and navigation functions via a navigationcontroller 146 and a GNSS controller 148. The mobile device 128 may beprovided with a wireless transceiver 142 in communication with a Wi-Ficontroller 150, a Bluetooth controller 152, a RFID controller 154, anNFC controller 156, and other controllers (not shown), configured tocommunicate with the wireless transceiver 132 of the computing platform104. The mobile device 128 may be further provided with a non-volatilestorage 158 to store various mobile application 160 and mobile data 162.

The computing platform 104 may be further configured to communicate withvarious components of the vehicle 102 via one or more in-vehicle network166. The in-vehicle network 166 may include, but is not limited to, oneor more of a controller area network (CAN), an Ethernet network, and amedia-oriented system transport (MOST), as some examples. Furthermore,the in-vehicle network 166, or portions of the in-vehicle network 166,may be a wireless network accomplished via Bluetooth low-energy (BLE),Wi-Fi, UWB, or the like.

The computing platform 104 may be configured to communicate with variousECUs 168 of the vehicle 102 configured to perform various options. Forinstance, the computing platform may be configured to communicate with aTCU 170 configured to control telecommunication between vehicle 102 anda wireless network 172 through a wireless connection 174 using a modem176. The wireless connection 174 may be in the form of variouscommunication network e.g. a cellular network. Through the wirelessnetwork 172, the vehicle may access one or more servers 178 to accessvarious content for various purposes. It is noted that the termswireless network and server are used as general terms in the presentdisclosure and may include any computing network involving carriers,router, computers, controllers or the like configured to store data andperform data processing functions and facilitate communication betweenvarious entities. The ECUs 168 may further include a powertrain controlmodule (PCM) 180 configured to provide operate powertrain of the vehicle102. For instance, the PCM 180 may be configured to start the vehicleresponsive to receiving a command from the mobile device 128 via the TCU170. The ECUs 168 may further include a HVAC controller 182 configuredto control a climate system of the vehicle 102. For instance, the HVACcontroller 182 may be configured to operate air-conditioning (AC),heating, seat ventilation heating or the like to provide the user with acustomized cabin condition. The computing platform 104 may be furtherconfigured to communicate with various vehicle sensors 184 via thein-vehicle network 166 configured to measure various data of the vehicle102. For instance, the sensors 184 may include a temperature sensor, acamera, a radar, a lidar, or the like.

Referring to FIG. 2, an example schematic diagram 200 of the vehiclesystem of one embodiment of the present disclosure is illustrated. Withcontinuing reference to FIG. 1, in the present example, the server 178may be configured to calculate a vehicle start time for the vehicle 102a using information from various sources. The server 178 may beconfigured to obtain a weather condition 202 for the location of thevehicle 102 a from a cloud 204 which may include various local or remoteservers associated with various entities. The server 178 may beconfigured to receive a user desired temperature 206 from the mobiledevice 128 associated with the user. The user may manually set thedesired temperature 206 for each ride via the mobile device 128.Additionally or alternatively, the desired temperature 206 may beassociated with a user profile and adjusted for different ride dependingon various factors such as weather, outside temperature, season or thelike. The user may further schedule a ride by manually inputting adeparture time via the via the mobile device 128. Additionally oralternatively, the server 178 may be configured to access a usercalendar 208 associated with the user to determine a time for each ride.The user calendar 208 may be stored in the mobile device 128 and/orfurther synchronized to the cloud 204 for the server 178 to access.Additionally, an estimated fuel level at the desired drive start timefor the vehicle 102 may be visually provided for the user to considersetting the desired temperature. For instance, in a winter situation,setting a higher desired cabin temperature may make the vehicle idlelonger and consumer more fuel. If a user opts to have the vehicle 102set to sixty five (65) degree F., an estimated fuel level of 60%remaining may be provided to the user. Whereas if the user opts forsixty (60) degree F., the estimated fuel remaining may be 62%, saving 2%fuel as compared with the former. The user may consider the fuel levelwhile setting the temperature.

The server 178 may be further configured to communicate with a pluralityof fleet vehicles 102 each configured to support the remote start andtemperature report features. For instance, the user may be associatedwith the vehicle 102 a, whereas the rest of the fleet vehicles 102 arethose located within the same geofence with the vehicle 102 a forreferences. The geofence may be predefined by the system to reflect anarea with similar weather conditions. For instance, the geofence may bedefined by a zip code or postal code of a region. Alternatively, theserver 178 may be configured to define a customized geofence using theweather condition 202 from the cloud. The server may be configured toobtain a vehicle perceived condition 210 from the fleet vehicles withinthe geofence indicative of an actual temperature and condition (e.g.sun, shade) perceived by the vehicle as the weather condition 202 whichmay only be a forecast may be inaccurate, the vehicle perceivedcondition 210 may be helpful to determine vehicle ventilation in somecases when a temperature difference between the current cabintemperature and the external ambient air temperature is great. Forinstance, lowering vehicle windows to ventilate heat trapped through thegreenhouse effect would provide an efficient cooling process in additionto A/C. Moon roofs or other electronically controlled vents may also beused for heat ventilation. The server 178 may be further configured toobtain vehicle configurations 212 and vehicle historic temperatures 214from the fleet vehicles 102 to more accurately calculate the timerequired for the vehicle 102 a to reach the desired temperature. Thevehicle configuration 212 may include information about configurationsthat may affect the performance of the vehicle HVAC system. Forinstance, the vehicle configuration may include information aboutvehicle brand, model, year, engine power, AC compressor power, type ofpowertrain (e.g. gasoline engine, electric motor, hybrid) or the like.Vehicle configuration 212 from fleet vehicles 102 with similarconfigurations to the vehicle 102 a of the user may be given more weightduring calculation. The vehicle historic temperature 214 may includehistoric temperature data of the fleet vehicles 102 such as a length oftime for the vehicles to reach a desired temperature from a startingtemperature. The historic temperature 214 may be useful for the server178 to analyzing at a specific timeframe of a day within the samegeofence.

Referring to FIG. 3, an example flow diagram for a remote start process300 of the vehicle system of one embodiment of the present disclosure isillustrated. With continuing reference to FIGS. 1 and 2, at operation302, the server 178 accesses to the user mobile device 128 to obtain thecalendar of the user and determine a scheduled ride using the calendarat operation 304. The calendar may include information about ameeting/event scheduled at a certain time at a certain location. Theserver 178 may calculate the time required to arrive the meetinglocation and therefore obtain the departure time of the ride. Additionor alternatively, the calendar may be obtained elsewhere (e.g. from thecloud 204) as discussed above. At operation 306, the server 178 receivesa desired temperature of the user from the mobile device 128.Additionally, the server 178 may receive a user profile from the mobiledevice 128. The user profile may include various preferences includingthe desired temperature of the user. In case of a ride sharingsituation, the user profile may further identify one of the fleetvehicles 102 for the scheduled ride. Responsive to determining thedesired temperature as well as the identity of the designated vehicle(e.g. vehicle 102 a), at operation 308, the server 178 receives vehicledata from the vehicle 102 a designated to the scheduled ride. Thevehicle data may include the current location of the vehicle 102 a.Additionally, the vehicle data may include a vehicle perceivedtemperature 210, vehicle configuration 212, and/or vehicle historictemperature 214 of the vehicle 102 a for analysis. With the location ofthe vehicle 102 a, the server 178 receives a weather condition 202 forthe vehicle location around the time of the scheduled ride at operation310. At operation 312, the server 178 determines a geofence within whichthe vehicle 102 a. is located at operation 310. As discussed above, thegeofence may be predetermined by the system. Alternatively, the server178 may be configured to calculate the geofence using the weathercondition 202 received from the cloud 204. For instance, if the weathercondition 314 reports a specific weather condition (e.g. rain) in anarea within with the vehicle 102 a is located, the server 178 mayarbitrarily define the geofence to be the area of that specific weathercondition for more accurate analysis.

With the geofence determined, at operation 314, the server 178 obtainsvehicle data from fleet vehicles 102 b . . . 102 n located within thegeofence for analysis. As discussed above, the vehicle data may includevehicle perceived temperature 210, vehicle configuration data 212,and/or vehicle historic temperature 214. At operation 316, the server178 analyzes the vehicle data from the designated vehicle 102 a as wellas the fleet vehicles 102 b . . . 102 n, and calculate the minimum timerequired to the designated vehicle 102 a to reach the desiredtemperature. With the minimum time calculated, the server 178 sends theinstruction to start to the vehicle 102 a at operation 318. Theinstruction to start may further include instructions for the HVACcontroller to operate the cabin climate of the vehicle 102. Responsiveto receiving the instruction from the server 178, the vehicle 102 astarts and activates the HVAC system at operation 320. At operation 322,the vehicle 102 a detects the user starts the ride. In response, thevehicle records the current cabin temperature as compared with thedesired temperature as a part of the vehicle historic temperature 214for future reference. Additionally, at operation 324, the vehicle 102 asends the current cabin temperature to the server 178 for recordation.The server 178 compares the cabin temperature at the time the userstarts the ride with the desired temperature to adjust futurecalculations.

In certain situations, the vehicle 102 a may not be able to startresponsive to the instruction from the server 178 for various reasonssuch as the vehicle is parked in an enclosed environment as detected viathe sensors 184. In this case, the vehicle 102 a may reject the startinstruction and respond a message to the server 178 about the situation.The server 178 may forward the message to the mobile device 128 toinform the failure to start the vehicle 102 a.

While exemplary embodiments are described above, it is not intended thatthese embodiments describe all possible forms of the invention. Rather,the words used in the specification are words of description rather thanlimitation, and it is understood that various changes may be madewithout departing from the spirit and scope of the invention.Additionally, the features of various implementing embodiments may becombined to form further embodiments of the invention.

What is claimed is:
 1. A server, comprising: a processor, programmed toreceive a vehicle location from a vehicle, receive a weather conditionof the vehicle location from a cloud server, responsive to receiving acalendar of a user including an event, calculate a departure time basedon the vehicle location. and a location of the event, responsive toreceiving a desired cabin. temperature of the user from a mobile device,calculate a minimum time for the vehicle to reach the desired cabintemperature based on the weather condition, calculate a vehicle starttime using the departure time and the minimum time, and send aninstruction to the vehicle to start at the vehicle start time.
 2. Theserver of claim 1, wherein the processor is further programmed to:receive a vehicle-perceived condition, a vehicle configuration, and avehicle historic temperature from the vehicle, wherein the calculationof the minimum time is further based on the vehicle-perceived condition,the vehicle configuration, and the vehicle historic temperature.
 3. Theserver of claim 2, wherein the processor is further programmed to:calculate a geofence using the vehicle location, identify a fleetvehicle within the geofence, and receive a fleet-vehicle-perceivedcondition, a fleet vehicle configuration, and a fleet vehicle historictemperature from the fleet vehicle, wherein the calculation of theminimum time is further based on the fleet-vehicle-perceived condition,the fleet vehicle configuration, and the fleet vehicle historictemperature as received from the fleet vehicle.
 4. The server of claim3, wherein the processor is further programmed to: calculate thegeofence accounting for the weather condition as an area enclosing thevehicle location.
 5. The server of claim 3, wherein the processor isfurther programmed to: calculate the geofence using a zip code for anarea in which the vehicle location is located.
 6. The server of claim 3,wherein the processor is further programmed to: receive a user profileidentifying the vehicle from the mobile device associated with the user;and request for the vehicle location of the vehicle as identified. 7.The server of claim 3, wherein the processor is further programmed to:receive an actual cabin temperature as the user starts to use thevehicle; and compare the actual cabin temperature with the desired cabintemperature for future adjustment of temperature.
 8. The server of claim3, wherein the processor is further programmed to: responsive toreceiving a failure message from the vehicle indicative of a failure ofthe vehicle to start responsive to the instruction, send the failuremessage to the mobile device.
 9. The server of claim 3, wherein theprocessor is further programmed to: responsive to receiving a seconddeparture time manually input by the user via the mobile device,override the departure time using the second departure time.
 10. Theserver of claim 3, wherein the instruction includes a command for aheating ventilation air-conditioning controller of the vehicle.
 11. Amethod for a server, comprising: receiving a user profile from a mobiledevice associated with a user identifying a vehicle for a ride and adesired cabin temperature; receiving a vehicle location, a vehicleperceived condition, a vehicle configuration, and a vehicle historictemperature from the vehicle as identified; obtaining a calendarassociated with the user including an event having an event location;calculating a departure time based on the vehicle location and the eventlocation; receiving a weather condition of the vehicle location from acloud server; calculating a minimum time for the vehicle to reach thedesired cabin temperature based on the weather condition, the vehicleperceived condition, the vehicle configuration, and the vehicle historictemperature; calculating a vehicle start time using the departure timeand the minimum time; and sending an instruction. to the vehicle tostart at the vehicle start time.
 12. The method of claim 11, furthercomprising: calculating a geofence enclosing the vehicle location;identifying a plurality of fleet vehicles within the geofence; receivinga fleet vehicle perceived condition, a fleet vehicle configuration, anda fleet vehicle historic temperature from the fleet vehicles; andcalculating the minimum time accounting for the fleet vehicle perceivedtemperature, the fleet vehicle configuration, and the fleet vehiclehistoric temperature as received from the fleet vehicles.
 13. The methodof claim 12, further comprising: calculating the geofence accounting forthe weather condition of an area enclosing the vehicle location.
 14. Themethod of claim 12, further comprising: calculating the geofence using azip code for an area which the vehicle location falls into.
 15. Themethod of claim 12, further comprising: receiving an actual cabintemperature as the user starts to use the vehicle; and comparing, theactual cabin temperature with the desired cabin temperature for futureadjustment.
 16. The method of claim 12, further comprising: responsiveto receiving a failure message from the vehicle indicative of failing tostart, sending the failure message to the mobile device.
 17. The methodof claim 12, further comprising: responsive to receiving a seconddeparture time manually input by the user via the mobile device,overriding the departure time using the second departure time.
 18. Themethod of claim 12, wherein the instruction includes a command for aheating ventilation air-conditioning controller of the vehicle.
 19. Anon-transitory computer-readable medium comprising instructions that,when executed by a processor of a computer, cause the computer to:receive a user profile from a mobile device associated with a useridentifying a vehicle for a ride and a desired cabin temperature;receive a vehicle location, a vehicle perceived condition, a vehicleconfiguration, and a vehicle historic temperature from the vehicle asidentified; obtain a calendar associated with the user including anevent having an event location; calculate a departure time based on thevehicle location and the event location; receive a weather condition ofthe vehicle location from a cloud server; calculate a geofence enclosingthe vehicle location; responsive to identifying a plurality of fleetvehicles within the geofence, receive a fleet vehicle perceivedcondition, a fleet vehicle configuration, and a fleet vehicle historictemperature from the fleet vehicles; calculate a minimum time for thevehicle to reach the desired cabin temperature based on the weathercondition, the vehicle perceived condition, the vehicle configuration,the vehicle historic temperature as received from the vehicle, the fleetvehicle perceived temperature, the fleet vehicle configuration, and thefleet vehicle historic temperature as received from the fleet vehicles;calculate a vehicle start time using the departure time and the minimumtime; and send an instruction to the vehicle to start at the vehiclestart time.
 20. The non-transitory computer-readable medium of claim 19,further comprising instructions that, when executed by a processor of acomputer, cause the computer to: calculate the geofence using a zip codefor an area which the vehicle location falls into.